New package: zed-0.231.1 by JudahJL · Pull Request #59813 · void-linux/void-packages

JudahJL · 2026-04-07T22:46:56Z

Testing the changes

I tested the changes in this PR: YES

New package

This new package conforms to the package requirements: YES

Local build testing

I built this PR locally for my native architecture, (x86_64-glibc)
I built this PR locally for these architectures (crossbuilds):
- aarch64-glibc

Nizarjh · 2026-04-08T11:02:50Z

dupllicate #58659

JudahJL · 2026-04-08T14:55:36Z

@Nizarjh I apologize for the duplicate pr.
didnt notice another pending pr.
I just wanted to add zed to the main repo as quickly as possible to use it asap.
Note: This one doesnt build the remote_server for now(commented it out). will do it at next update or if asked to do in review

Nizarjh · 2026-04-08T18:41:43Z

@Nizarjh I apologize for the duplicate pr. didnt notice another pending pr. I just wanted to add zed to the main repo as quickly as possible to use it asap. Note: This one doesnt build the remote_server for now(commented it out). will do it at next update or if asked to do in review

u can use my template and patches for your own)

srcpkgs/zeditor/template

Nizarjh · 2026-04-09T13:42:15Z

u need also change binary name from zed to smth with patch. u can look how i made this in my pr. But my pacth is not actual to new version. so do your own for this version of zed

JudahJL · 2026-04-09T13:53:45Z

u need also change binary name from zed to smth with patch. u can look how i made this in my pr. But my pacth is not actual to new version. so do your own for this version of zed

@Nizarjh I don't need to use that patch. I'm renaming the executable at do_install stage. There's also an additional check in the check build CI/CD that ensures no name conflicts occur in the executables(which successfully passes)

Nizarjh · 2026-04-09T13:56:29Z

u need also change binary name from zed to smth with patch. u can look how i made this in my pr. But my pacth is not actual to new version. so do your own for this version of zed

@Nizarjh I don't need to use that patch. I'm renaming the executable at do_install stage. There's also an additional check in the check build CI/CD that ensures no name conflicts occur in the executables(which successfully passes)

oh i see. Sorry :)

Duncaen · 2026-04-09T15:56:49Z

srcpkgs/zeditor/template

+pkgname=zeditor
+version=0.231.1
+revision=1
+archs="x86_64 aarch64"


Suggested change

archs="x86_64 aarch64"

archs="x86_64* aarch64*"

Didn't compile successfully on musl versions locally

Then that is a merge blocker, there is no reason it shouldn't work with musl.

Because of dependencies not existing in one of the musl version. For details, I'll let you know when I get home

x86_64-linux-musl:

ERROR: Could not find package 'cross-x86_64-linux-musl' => ERROR: cross-x86_64-linux-musl-0.37_5: cannot be built, it's currently broken; see the build log: => ERROR: cross-x86_64-linux-musl-0.37_5: Can't build crosstoolchain to itself

aarch64-musl:

error: failed to run custom build command for `prost-build v0.9.0` Caused by: process didn't exit successfully: `/builddir/zed-0.231.1/target/release/build/prost-build-b23121bcf79afb3f/build-script-build` (exit status: 101) --- stderr thread 'main' (12773) panicked at /host/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/prost-build-0.9.0/build.rs:105:10: Failed to find the protoc binary. The PROTOC environment variable is not set, there is no bundled protoc for this platform, and protoc is not in the PATH note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Duncaen · 2026-04-09T15:58:01Z

srcpkgs/zeditor/template

@@ -0,0 +1,61 @@
+# Template file for 'zeditor'
+pkgname=zeditor


I don't think the package name is a good choice.

https://zed.dev/docs/development/linux#notes-for-packaging-zed

Binary != package name and you named the binary different from that too. There is no reason to not name the package "zed".

https://zed.dev/docs/development/linux#other-things-to-note

There are a couple of other zed binaries that may be present on Linux systems (1, 2). If you want to rename our CLI binary because of these issues, we suggest zedit, zeditor, or zed-cli.

initial thoughts were to make the binary and package name both to zeditor, so its easy to remember.

Then zed-editor(GUI) and zeditor(cli) was confusing, therefore chose zed-cli

We generally use upstream package names, and since there is no existing "zed" package, I don't think there is a reason to not use that name.

name for cli?

srcpkgs/zeditor/template

Duncaen · 2026-04-09T16:07:05Z

srcpkgs/zeditor/template

+	local app_id="dev.zed.Zed"
+	local app_cli_name="zed-cli"


Just remove those variables, they are mostly useless. Also not sure if "zed-cli` is a good choice, no other distribution calls it that.

Vars are there for easy refactoring only. Couldn't think of better names. Suggestions are welcome

We don't optimize for easy refactoring. Its not a variable, don't make it more complicated than it has to be.

I think it's better rename to zed-editor. package name also

https://github.com/void-linux/void-packages/pull/59813/changes#diff-9648758f25f2c11ddeb1d522b1e46f036962042cb4270d1cb9b7b7b85893b2beR45

zed-editor is already used. the suggested names were zedit, zeditor, or zed-cli.

Thought to name it zeditor for both package name and cli but then zed-editor(GUI) and zeditor(cli) was confusing, therefore chose zed-cli

suggested names are from here:
https://zed.dev/docs/development/linux#other-things-to-note

There are a couple of other zed binaries that may be present on Linux systems (1, 2). If you want to rename our CLI binary because of these issues, we suggest zedit, zeditor, or zed-cli.

tranzystorekk added the new-package This PR adds a new package label Apr 7, 2026

JudahJL force-pushed the newpkg-zeditor branch from 0117a4c to 3cab146 Compare April 8, 2026 07:10

JudahJL force-pushed the newpkg-zeditor branch from 3cab146 to 41a8e4f Compare April 8, 2026 14:46

Duncaen requested changes Apr 8, 2026

View reviewed changes

srcpkgs/zeditor/template Outdated Show resolved Hide resolved

JudahJL force-pushed the newpkg-zeditor branch from 863c9d7 to 6843c3b Compare April 9, 2026 01:48

Nizarjh suggested changes Apr 9, 2026

View reviewed changes

srcpkgs/zeditor/template Outdated Show resolved Hide resolved

JudahJL force-pushed the newpkg-zeditor branch 2 times, most recently from 58e12fe to abf6b69 Compare April 9, 2026 02:18

JudahJL requested review from Duncaen and Nizarjh April 9, 2026 03:35

Nizarjh approved these changes Apr 9, 2026

View reviewed changes

JudahJL force-pushed the newpkg-zeditor branch from 5d78328 to 1b32217 Compare April 9, 2026 14:22

JudahJL changed the title ~~New package: zeditor-0.230.2~~ New package: zeditor-0.231.1 Apr 9, 2026

Duncaen requested changes Apr 9, 2026

View reviewed changes

New package: zeditor-0.230.2

06a3481

JudahJL force-pushed the newpkg-zeditor branch from 1b32217 to 06a3481 Compare April 9, 2026 20:06

JudahJL changed the title ~~New package: zeditor-0.231.1~~ New package: zed-0.231.1 Apr 9, 2026

		@@ -0,0 +1,61 @@
		# Template file for 'zeditor'
		pkgname=zeditor

Conversation

JudahJL commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Testing the changes

New package

Local build testing

Uh oh!

Nizarjh commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JudahJL commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Nizarjh commented Apr 8, 2026

Uh oh!

Uh oh!

Uh oh!

Nizarjh commented Apr 9, 2026

Uh oh!

JudahJL commented Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Nizarjh commented Apr 9, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JudahJL Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JudahJL Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Duncaen Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JudahJL Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JudahJL Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JudahJL Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

JudahJL commented Apr 7, 2026 •

edited

Loading

Nizarjh commented Apr 8, 2026 •

edited

Loading

JudahJL commented Apr 8, 2026 •

edited

Loading

JudahJL commented Apr 9, 2026 •

edited

Loading

JudahJL Apr 9, 2026 •

edited

Loading

JudahJL Apr 9, 2026 •

edited

Loading

Duncaen Apr 9, 2026 •

edited

Loading

JudahJL Apr 9, 2026 •

edited

Loading

JudahJL Apr 9, 2026 •

edited

Loading

JudahJL Apr 9, 2026 •

edited

Loading